Prizm Content Connect
Linux Installation
Getting Started with PCC > Installation > Linux > Linux Installation

Prizm Content Connect (PCC) installation is designed to be very straightforward for Linux environments. Follow the steps provided in this section.

You need to uninstall the prior version of PCC before installing the new version.

Some steps may be specific to a particular Linux distribution; these steps will be labeled as being specific to one of the following: 

The hash sign (#) is used to represent the command prompt. Do not include it when entering the commands.

Make sure you log in as root to the machine.

Step 1 - Download & Install Prizm Content Connect

  1. Download the proper package for your distribution and architecture and install as root:

Red Hat, Fedora, CentOS, and older Linux Distributions

32-bit: prizmcc_<version>.i686.rpm
64-bit: prizmcc_<version>.x86_64.rpm

32-bit: prizmconverter_<version>.i686.rpm
64-bit: prizmconverter_<version>.x86_64.rpm

Example
Copy Code

# yum install –-nogpgcheck prizmcc_<version>.x86_64.rpm

# yum install -–nogpgcheck prizmconverter_<version>.x86_64.rpm
Debian (Ubuntu) Linux Distributions

32-bit: prizmcc_<version>.i386.deb
64-bit: prizmcc_<version>.amd64.deb

32-bit: prizmconverter_<version>.i386.deb
64-bit: prizmconverter_<version>.amd64.deb

Example
Copy Code

# sudo apt-get install gdebi-core
# sudo gdebi prizmcc_<version>.amd64.deb

# sudo apt-get install gdebi-core
# sudo gdebi prizmconverter_<version>.amd64.deb

Generic .tar.gz Distribution

We also provide a generic .tar.gz package. You will need to install the dependencies described in the Requirements section. Once the dependencies are installed, you can install the .tar.gz with the following commands as root:

Example
Copy Code

# tar –xzvf prizmcc_<version>.x86_64.tar.gz
# cp –R prizm /usr/share
# cd /usr/share/prizm

# tar –xzvf prizmconverter_<version>.x86_64.tar.gz
# cp –R prizm /usr/share
# cd /usr/share/prizm

 

Step 2 - Configure

  1. Continuing as root, change to the installation location: /usr/share/prizm and run setup.sh. This will confirm your LibreOffice installation location. Run the Prizm Licensing Utility (PLU), and configure the PCC for its first run:

setup.sh launches the Prizm License Utility (PLU), which is a GUI application. Depending on how you have X11 configured, you might need to run 'xhost +' as the logged in user to allow the PLU launched by the root user to access X11. You can disable X11 access for root by executing 'xhost –' when you are done.
Example
Copy Code

# ./setup.sh

Using office at odc_installation=/opt/libreoffice4.2
Select the type of license you want to acquire:
    1) Evaluation [e]
    2) Deployment [d]
Choose 1 or 2: d
Select the type of deployment license you have:
    1) Node Locked [n]
    2) OEM         [o]
Choose 1 or 2: o
Provide the solution name: PCC9
Provide the OEM license key provided to you: 2.0...
Your deployment license was acquired successfully.
./scripts/pccis.sh start
Starting Prizm Content Connect Information Services...
Starting Nginx process...
Starting PCCIS Watchdog process...
PCCIS Watchdog has been started correctly.
  1. For a production installation, you will want to configure where log files are stored and ensure that Nginx logs are rotated and pruned. See the section How to Configure Log File Locations. 

 

Step 3 - Verify that the Installation was Successful   

  1. Browse to the following either via URL or through a browser:

http://127.0.0.1:18681/PCCIS/V1/Service/Current/Info

You should receive a response like this:

Example
Copy Code 
{"serviceStatus":"running","licenseStatus":"licensed as 'PCC9'","instances":[{"serviceStatus":"running","pccisVersion":"9.0.1023.5421","runtimeVersion":"4.0.30319.17020","operatingSystem":"Unix 3.13.0.24","startTime":"2014-07-15T16:37:59.8831600Z","instanceId":"ip-10-7-149-236","childServices":[{"name":"PCC Imaging Proxy Server","serviceStatus":"running","version":"9.0.1023.4357"},{"name":"PCC Imaging Conversion Service","serviceStatus":"running","version":"1.0.0023.4890"},{"name":"PCC Raster Conversion Service","serviceStatus":"running","version":"2.0.0023.4222"}]}]}

Step 4 - Configure on CentOS 5.x

PCC will not work on a CentOS 5.x system with the default LibreOffice. For this purpose you need to download and install LibreOffice from libreoffice.org as described below:

  1. Install the latest stable version of LibreOffice for your OS. Download and install it from this location: http://www.libreoffice.org/download
  2. Follow LibreOffice Installation instructions from this location: http://www.libreoffice.org/get-help/installation/linux/

LibreOffice Desktop Integration for Linux is not needed; you do not need to complete those steps.

The LibreOffice installation might fail if you have LibreOffice or any other application already listening on any of the following ports: 18580, 18584, 18585, 18586, 18590, 18591, 18592, 18593, 18680.

By default, Prizm Content Connect installs the proxy service on port 18680 and uses 3 of the following ports for conversion purposes: 18580, 18584, 18585, 18586, 18591, 18592, 18593. You can add more ports as your traffic increases.
  1. Locate root folder of your LibreOffice installation. The LibreOffice is usually located in the following directory: /opt/libreoffice4.x
  1. Edit <prizm-install>/conf/proxyserver_jar.properties and change following parameter to fit the root location of LibreOffice:
Example
Copy Code 
Office Document converter installation base directory
#odc_installation=/usr/share/prizm/libreoffice
odc_installation=/opt/libreoffice4.3
  1. Save proxyserver_jar.properties, restart Prizm service and check proxyserver.log to make sure PCC uses the installed LibreOffice.

Step 5 - Installation Complete

Your installation is now complete.

How to Install Common Certificate Authority Root Certificates on Linux

The following commands should all be run as root. Additionally, if prompted for addition/removal permission, then yes/no should be entered as the response.

  1. Install all Mozilla's root certificates. This command will install all the root certificates Mozilla accepts, prompting only to remove certificates that Mozilla doesn't list, adding all it does trust without prompt. This should make HTTPS work for any system that Firefox works with:
Example
Copy Code 
/usr/share/prizm/mono/64/bin/mozroots --machine --import --ask-remove
  1. Pull certificates from an https connection to accept:
Example
Copy Code 
/usr/share/prizm/mono/64/bin/certmgr -ssl -m https://servertoadd

As long as the server includes the entire chain to root, this will allow the certificate to authenticate. This will generally be the case for self-signed test certificates. For more complex situations, any required items from the chain will need to be added manually.

  1. Manually add the certificate from the file:
Example
Copy Code 
/usr/share/prizm/mono/64/bin/certmgr -add -c -m /path/to/certificatefile

The certificate stores the certificates at: /usr/share/.mono/certs/.

 

 

©2014. Accusoft Corporation. All Rights Reserved.

Send Feedback